User-input scheduling of synchronization operation on a mobile device based on user activity

ABSTRACT

Data is synchronized between a mobile device and a computing device over a wireless link. Synchronization operations are scheduled according to a synchronization schedule that is based on a current time of day. In one embodiment, the day can be divided into different time periods by the user. The user can also specify the frequency with which synchronization operations are to be performed during each specified period.

CROSS-REFERENCE TO RELATED APPLICATION(S)

The present application is a continuation of U.S. patent applicationSer. No. 15/799,524, filed Oct. 31, 2017, which is a continuation ofU.S. patent application Ser. No. 14/691,059, filed Apr. 20, 2015, nowU.S. Pat. No. 9,838,985, issued Dec. 5, 2017, which is a continuation ofU.S. patent application Ser. No. 13/930,525, filed Jun. 28, 2013, nowU.S. Pat. No. 9,037,173, issued May 19, 2015, which is a continuation ofU.S. patent application Ser. No. 13/369,725, filed Feb. 9, 2012, nowU.S. Pat. No. 8,509,830, issued Aug. 13, 2013, which is a continuationof U.S. patent application Ser. No. 13/173,242, filed Jun. 30, 2011, nowU.S. Pat. No. 8,140,099, issued Mar. 20, 2012, which is a continuationof U.S. patent application Ser. No. 12/872,579, filed Aug. 31, 2010, nowU.S. Pat. No. 7,996,028, issued Aug. 9, 2011 which is a continuation ofU.S. patent application Ser. No. 10/641,380, filed Aug. 14, 2003, nowU.S. Pat. No. 7,809,384, issued Oct. 5, 2010, which claims benefit ofU.S. Provisional Patent Application No. 60/424,177, filed Nov. 5, 2002,the contents of each of which are hereby incorporated by reference intheir entireties.

BACKGROUND

The present invention relates to synchronization of objects betweenobject stores on two different computing devices. More particularly, thepresent invention relates to scheduling of synchronization operations onmobile devices.

Mobile devices include a broad range of computing and communicationdevices that are small enough to be conveniently carried by a user.Examples of such devices include mobile phones, personal digitalassistants, tablet PCs, and lap-top PCs.

Generally, the mobile device includes a processor, random access memory(RAM), and an input device such as a keyboard, touchpad or input buttonsand a display. The keyboard can be integrated with the display, such aswhen the keyboard is incorporated as a touch sensitive display. Acommunication interface is optionally provided and is commonly used tocommunicate with other computers. A replaceable or rechargeable batterypowers the mobile device. Optionally, the mobile device can receivepower from an external power source that overrides or recharges thebuilt-in battery.

While a wide variety of computing tasks and applications can beperformed by such mobile devices, personal information managers (PIMs)are particularly well suited to mobile devices. PIMs typically compriseapplications which enable the user of the mobile device to better managescheduling and communications, and other such tasks. Some commonlyavailable PIMs include scheduling and calendar programs, task lists,address books, and electronic mail (e-mail) programs. Some commonlycommercially available PIMs are sold under the trademarks “MICROSOFTSCHEDULE+” and “MICROSOFT OUTLOOK” and are commercially available fromMicrosoft Corporation of Redmond, Wash. In addition to PIMs, however,such mobile devices may also run different types of applications, suchas word processors, spread sheets, etc.

To provide users with as much freedom as possible, it is desirable toallow the user to access and change their application and. PIMinformation from any device they choose. Thus, the user should be ableto access their e-mail from a network terminal, a PDA, and a tablet PC,for example.

However, allowing the user to access and change their information fromany desired source means that the devices must be able to communicatewith each other to indicate changes to the information. The process oftwo devices sharing changes in the application and/or PIM information isknown as synchronization.

In general, synchronization is not a continuous process. In other words,a mobile device does not continually try to synchronize its data becausethat would waste limited wireless bandwidth and place an undue drain onthe mobile device's battery. Instead, synchronization is performedperiodically. In addition, since the mobile device is not always in use,it is wasteful to have a server or desktop computer periodically attemptto establish a connection with the mobile device to performsynchronization. Instead, the mobile device is responsible forestablishing a connection to perform synchronization.

When scheduling synchronization operations through a wirelessconnection, such as a cellular connection, a number of concerns presentthemselves. First, it can be desirable to have data be as up-to-date aspossible. This requires synchronization (sync) to be performedfrequently. However, the synchronization process does require arelatively high amount of power and can thus affect the remainingbattery life of the mobile device. Similarly, cellular connectioncharges often apply. Since frequent sync operations require frequentcellular connection to a synchronization server, the costs associatedwith these connections can become relatively large. Also, cellularconnection costs can increase rather significantly, when connection ismade to a roaming mobile device. Thus, frequent sync operations,requiring frequent connections during roaming, can also undesirablyincrease the cost of synchronization.

SUMMARY

An aspect of the present disclosure is directed to a mobile devicehaving at least one computer storage medium. The mobile device includesa synchronization component retained on the at least one computerstorage medium, and configured to perform synchronization operationsthat synchronize data between the mobile device and a computing deviceover a wireless link. The mobile device also includes a synchronizationschedule retained on the at least one computer storage medium, thesynchronization schedule including a peak time period and a non-peaktime period for performing the synchronization operations. The mobiledevice further includes a user interface retained on the at least onecomputer storage medium, where the user interface includes a first inputcomponent configured to designate a time period throughout a day as thepeak time period or the non-peak time period, and a second inputcomponent configured to set at least one frequency at which thesynchronization operations are to be performed during the peak timeperiod, during the non-peak time period, or during both the peak timeperiod and the non-peak time period.

Another aspect of the present disclosure is directed to a mobile devicehaving at least one computer storage medium, where the mobile deviceincludes a synchronization schedule retained on the at least onecomputer storage medium. The synchronization schedule includes a peaktime period in which synchronization operations that synchronize databetween the mobile device and a computing device over a wireless linkare performed at a first frequency, and a non-peak time period in whichthe synchronization operations are performed at a second frequency. Themobile device also includes a user interface retained on the at leastone computer storage medium, where the user interface includes a firstinput component configured to designate a first time period throughoutthe day as the peak time period in response to a first user input, and asecond input component configured to set at least one of the firstfrequency and the second frequency in response to a second user input.

Another aspect of the present disclosure is directed to a method forsynchronizing data between a mobile device and a computing device over awireless link. The method includes accessing a synchronization scheduleretained on at least one computer storage medium of at least one of themobile device and the computing device, where the synchronizationschedule includes a peak time period and a non-peak time period forperforming synchronization operations that synchronize data between themobile device and the computing device. The method also includesdesignating a time period throughout a day as the peak time period orthe non-peak time period, and setting at least one frequency at whichthe synchronization operations are to be performed during the peak timeperiod, during the non-peak time period, or during both the peak timeperiod and the non-peak time period. The method further includesperforming at least one of the synchronization operations.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating a basic environment of thepresent invention.

FIG. 2 is a block diagram of one embodiment of a conventional desktopcomputer used in conjunction with a mobile device in accordance with thepresent invention.

FIG. 3 is a simplified pictorial illustration of one embodiment of amobile device in accordance with the present invention.

FIG. 4 is a simplified pictorial illustration of another embodiment of amobile device in accordance with the present invention.

FIG. 5 is a simplified block diagram of one embodiment of the mobiledevice shown in FIG. 3 or 4.

FIG. 6 is an architectural block diagram illustrating one embodiment ofportions of the desktop computer shown in FIG. 2 and the mobile deviceshown in FIGS. 3-5 to illustrate synchronization of information storedin object stores on the desktop computer and the mobile device inaccordance with one embodiment of the present invention.

FIG. 7 is a more detailed block diagram of portions of sync enginesshown in FIG. 1.

FIGS. 8A and 8B are flow diagrams illustrating a normal synchronizationoperation in accordance with one embodiment of the present invention.

FIG. 9 illustrates one embodiment of a user interface in accordance withthe present invention.

FIG. 10 is a flow diagram illustrating scheduling of sync operationsduring peak and off-peak times in accordance with one embodiment of thepresent invention.

FIG. 11 is a flow diagram illustrating a real time response process forscheduling sync operations in accordance with one embodiment of thepresent invention.

FIGS. 12A-12C show user interfaces for selecting a real time responsefeature in accordance with different embodiments of the presentinvention.

DETAILED DESCRIPTION Overview

FIG. 1 is a block diagram of a typical system or environment 10 in whichthe present invention operates. Scheduling of synchronization operationsis discussed in detail later, but the present overview is provided forclarity only. System 10 includes mobile device 12 and a computing device14. Mobile device 12 includes first application program 16, secondapplication program 18, corresponding first and second object stores 20and 22, synchronization engine 24 and communication link 26. Computingdevice 14 includes first and second application programs 28 and 30,corresponding first and second object stores 32 and 34, synchronizationengine 36 and communication link 38. It will be appreciated that bothmobile device 12 and computing device 14 include a number of othercomponents (including, for example, components and timers used toschedule synchronization operations), which are discussed in greaterdetail below. However, for the purposes of the overview discussionpresented with respect to FIG. 1, the items set out above aresufficient.

In one illustrative embodiment of the present invention, applicationprograms 16 and 28 are personal information manager (PIM) programs,which support, for example, electronic mail messaging, scheduling,calendering, etc. Hereinafter, programs 16 and 28 will simply bereferred to as PIMs 16 and 28. Of course, PIMs 16 and 28 can beconfigured to support a wide variety of other features, such as tasklists and personalized address books, to name a few.

Object stores 20 and 32 are implemented in memory configured to store aplurality of individual records or objects, each comprising a pluralityof fields or properties related to PIMs 16 and 28. In one illustrativeembodiment, PIMs 16 and 28 are programs, such as that available underthe commercial designation “MICROSOFT OUTLOOK”, and object stores 20 and23 are configured to store objects, each of which having a plurality ofattributes or properties associated with electronic mail messaging, suchas a sender's name, the recipient's name, text messages, etc. Computingdevice 14 executes PIM 28 to maintain objects stored in store 32, andmobile device 12 executes program 16 to maintain objects stored inobject store 20. In one illustrative embodiment, each object in objectstore 20 comprises the same set of properties or attributes stored inobject store 32, or a subset of those properties or attributes.

Similarly, application programs 18 and 30 maintain objects on associatedobject stores 22 and 34, respectively. In one illustrative embodiment,application programs 18 and 30 are file system applications, such asthose available under the commercial designation “MICROSOFT WORD”. Itshould also be noted that any suitable number of other applicationprograms, and associated object stores, can be provided on mobile device12 and computing device 14. However, for the sake of simplicity, onlyprograms 16, 18, 28 and 30, and their associated object stores, aredescribed herein.

In one illustrative embodiment, the user desires to synchronize objectstores 20 and 32 and object stores 22 and 34. Thus, there are twoinstances of each object associated with the pair of object stores 20and 32 (one instance in object store 20 and one instance in object store32) and two instances of each object associated with the pair of objectstores 22 and 34 (one instance in object store 22 and one instance inobject store 34). When a user changes one instance of the object storedin either object store 22 or 34, the second instance of that object inthe other of stores 22 and 34 is out of sync and is desirably updatedthe next time mobile device 12 has two-way communication with computingdevice 14, so that both instances of the same object containsynchronized data. The same is true for instances of objects stored inobject stores 20 and 32.

In order to accomplish synchronization, synchronization components 24and 36 run on mobile device 12 and computing device 14, respectively.The synchronization components communicate with application programs 16,18, 28 and 30 (or directly with the associated object stores) throughany well defined interfaces to manage communication and synchronization.

Synchronization components 24 and 36 communicate with each other throughcommunication links 26 and 38. Communication links 26 and 38 areillustratively commercially available communication links using asuitable communications protocol. For instance, in one illustrativeembodiment, mobile device 12 is connected to computing device 14 with aphysical cable which communicates using a serial communicationsprotocol. Other communication mechanisms are also contemplated by thepresent invention, such as infrared (IR) communication, direct modemcommunication, remote dial-up-networking communication, communicationthrough commercially available network cards (i.e., using TCP/IP),remote access services (RAS), wireless modem, wireless cellular digitalpacket data (CDPD), short message services or other suitablecommunication mechanisms. Although the communication links are shown asbeing internal to mobile device 12 and computing device 14, thoseskilled in the art will recognize that portions of the communicationlinks exist outside of the devices. For example, the communication linkscan include communication servers located between mobile device 12 andcomputing device 14, other portions of the network forming thecommunication link (such as the cellular and PSTN networks) and adapterssuch as mobile device cradles.

Prior to discussing the synchronization process and associatedmechanisms in greater detail, the present discussion proceeds withrespect to a more detailed description of the components of mobiledevice 12 and an example computing device 14 for the sake of clarity.

Computing Device 14

Computing device 14 is only one example of a suitable computing deviceand is not intended to suggest any limitation as to the scope of use orfunctionality of the invention. Neither should computing device 14 beinterpreted as having any dependency or requirement relating to any oneor combination of components illustrated in the exemplary computingdevice 14.

The invention is operational with numerous other general purpose orspecial purpose computing system environments or configurations.Examples of well-known computing systems, environments, and/orconfigurations that may be suitable for use with the invention include,but are not limited to, personal computers, server computers, hand-heldor laptop devices, multiprocessor systems, microprocessor-based systems,set top boxes, programmable consumer electronics, network PCs,minicomputers, mainframe computers, telephony systems, distributedcomputing environments that include any of the above systems or devices,and the like.

The invention may be described in the general context ofcomputer-executable instructions, such as program modules, beingexecuted by a computer. Generally, program modules include routines,programs, objects, components, data structures, etc. that performparticular tasks or implement particular abstract data types. Theinvention may also be practiced in distributed computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a communications network. In a distributed computingenvironment, program modules may be located in both local and remotecomputer storage media including memory storage devices.

With reference to FIG. 2, an exemplary system for implementing theinvention includes a general-purpose computing device in the form of acomputer 110. Components of computer 110 may include, but are notlimited to, a processing unit 120, a system memory 130, and a system bus121 that couples various system components including the system memoryto the processing unit 120. The system bus 121 may be any of severaltypes of bus structures including a memory bus or memory controller, aperipheral bus, and a local bus using any of a variety of busarchitectures. By way of example, and not limitation, such architecturesinclude Industry Standard Architecture (ISA) bus, Micro ChannelArchitecture (MCA) bus, Enhanced ISA (EISA) bus, Video ElectronicsStandards Association (VESA) local bus, and Peripheral ComponentInterconnect (PCI) bus also known as Mezzanine bus.

Computer 110 typically includes a variety of computer readable media.Computer readable media can be any available media that can be accessedby computer 110 and includes both volatile and nonvolatile media,removable and non-removable media. By way of example, and notlimitation, computer readable media may comprise computer storage mediaand communication media. Computer storage media includes both volatileand nonvolatile, removable and non-removable media implemented in anymethod or technology for storage of information such as computerreadable instructions, data structures, program modules or other data.Computer storage media includes, but is not limited to, RAM, ROM,EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disks (DVD) or other optical disk storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other medium which can be used to store the desired informationand which can be accessed by computer 110. Communication media typicallyembodies computer readable instructions, data structures, programmodules or other data in a modulated data signal such as a carrier waveor other transport mechanism and includes any information deliverymedia. The term “modulated data signal” means a signal that has one ormore of its characteristics set or changed in such a manner as to encodeinformation in the signal. By way of example, and not limitation,communication media includes wired media such as a wired network ordirect-wired connection, and wireless media such as acoustic, RF,infrared and other wireless media. Combinations of any of the aboveshould also be included within the scope of computer readable media.

The system memory 130 includes computer storage media in the form ofvolatile and/or nonvolatile memory such as read only memory (ROM) 131and random access memory (RAM) 132. A basic input/output system 133(BIOS), containing the basic routines that help to transfer informationbetween elements within computer 110, such as during start-up, istypically stored in ROM 131. RAM 132 typically contains data and/orprogram modules that are immediately accessible to and/or presentlybeing operated on by processing unit 120. By way of example, and notlimitation, FIG. 2 illustrates operating system 134, applicationprograms 135, other program modules 136, and program data 137.

The computer 110 may also include other removable/non-removablevolatile/nonvolatile computer storage media. By way of example only,FIG. 2 illustrates a hard disk drive 141 that reads from or writes tonon-removable, nonvolatile magnetic media, a magnetic disk drive 151that reads from or writes to a removable, nonvolatile magnetic disk 152,and an optical disk drive 155 that reads from or writes to a removable,nonvolatile optical disk 156 such as a CD ROM or other optical media.Other removable/non-removable, volatile/nonvolatile computer storagemedia that can be used in the exemplary operating environment include,but are not limited to, magnetic tape cassettes, flash memory cards,digital versatile disks, digital video tape, solid state RAM, solidstate ROM, and the like. The hard disk drive 141 is typically connectedto the system bus 121 through a non-removable memory interface such asinterface 140, and magnetic disk drive 151 and optical disk drive 155are typically connected to the system bus 121 by a removable memoryinterface, such as interface 150.

The drives and their associated computer storage media discussed aboveand illustrated in FIG. 2, provide storage of computer readableinstructions, data structures, program modules and other data for thecomputer 110. In FIG. 2, for example, hard disk drive 141 is illustratedas storing operating system 144, application programs 145, other programmodules 146, and program data 147. Note that these components can eitherbe the same as or different from operating system 134, applicationprograms 135, other program modules 136, and program data 137. Operatingsystem 144, application programs 145, other program modules 146, andprogram data 147 are given different numbers here to illustrate that, ata minimum, they are different copies.

A user may enter commands and information into the computer 110 throughinput devices such as a keyboard 162, a microphone 163, and a pointingdevice 161, such as a mouse, trackball or touch pad. Other input devices(not shown) may include a joystick, game pad, satellite dish, scanner,or the like. These and other input devices are often connected to theprocessing unit 120 through a user input interface 160 that is coupledto the system bus, but may be connected by other interface and busstructures, such as a parallel port, game port or a universal serial bus(USB). A monitor 191 or other type of display device is also connectedto the system bus 121 via an interface, such as a video interface 190.In addition to the monitor, computers may also include other peripheraloutput devices such as speakers 197 and printer 196, which may beconnected through an output peripheral interface 190.

The computer 110 may operate in a networked environment using logicalconnections to one or more remote computers, such as a remote computer180, which can include mobile device 12. The remote computer 180 may bea personal computer, a hand-held device, a server, a router, a networkPC, a peer device or other common network node, and typically includesmany or all of the elements described above relative to the computer110. The logical connections depicted in FIG. 2 include a local areanetwork (LAN) 171 and a wide area network (WAN) 173, but may alsoinclude other networks. Such networking environments are commonplace inoffices, enterprise-wide computer networks, intranets and the Internet.In addition, the network connections between any of the nodes in thenetwork may include direct cable connections or wireless connections andthe connection between computer 110 and remote computer 180 may includeany number of nodes and/or routers.

When used in a LAN networking environment, the computer 110 is connectedto the LAN 171 through a network interface or adapter 170. When used ina WAN networking environment, the computer 110 typically includes amodem 172 or other means for establishing communications over the WAN173, such as the Internet. The modem 172, which may be internal orexternal, may be connected to the system bus 121 via the user inputinterface 160, or other appropriate mechanism. In a networkedenvironment, program modules depicted relative to the computer 110, orportions thereof, may be stored in the remote memory storage device. Byway of example, and not limitation, FIG. 2 illustrates remoteapplication programs 185 as residing on remote computer 180. It will beappreciated that the network connections shown are exemplary and othermeans of establishing a communications link between the computers may beused.

Dynamically linked libraries (DLLs), comprising a plurality ofexecutable functions are associated with PIM 28 and application 30 forexecution by processor 62. Interprocessor and intercomponent calls arefacilitated preferably using the component object model (COM) as iscommon in programs written for Microsoft “WINDOWS” brand operatingsystems. Briefly, when using COM, a software component such as a DLL hasa number of interfaces. Each interface exposes a plurality of methods,which can be called individually to utilize different services offeredby the software component. In addition, interfaces are provided suchthat methods or functions can be called from other software componentswhich optionally receive and return one or more parameter arguments.

In general, the DLLs associated with PIM 28 and program 30 are designedspecifically to work in conjunction with PIM 28 and program 30 and toexpose desktop synchronization interfaces that function according to asynchronization protocol. The DLLs, in turn, call interfaces exposed byPIM 28 and program 30 in order to access data representing individualproperties of objects maintained in object stores 32 and 34. Objectstores 32 and 34, of course, can reside in any one of the suitablememory components described with respect to FIG. 2.

Mobile Device 12

FIG. 3 is a simplified pictorial illustration of one preferredembodiment of a mobile device 12 which can be used in accordance withthe present invention. In one embodiment, mobile device 12 includes aminiaturized keyboard 300, display 302 and stylus 304. In the embodimentshown in FIG. 3, display 302 is a liquid crystal display (LCD) whichuses a contact sensitive display screen in conjunction with stylus 304.Stylus 304 is used to press or contact the display 302 at designatedcoordinates to accomplish certain user input functions. Miniaturizedkeyboard 300 is illustratively implemented as a miniaturizedalpha-numeric keyboard, with any suitable and desired function keyswhich are also provided for accomplishing certain user input functions.

FIG. 4 is an illustration of a different embodiment of mobile device 12.Mobile device 12, as shown in FIG. 4, includes a touch sensitive screen402 which can be used, in conjunction with stylus 404, to accomplishcertain user input functions.

It should be noted that the displays 302 and 402 for the mobile devicesshown in FIGS. 3 and 4 can be the same size as one another, or differentsizes from one another, but would typically be much smaller than aconventional display used with a desktop computer. For example, displays302 and 402 shown in FIGS. 3 and 4 may be defined by a matrix of only240.times.320 coordinates, or 160.times.160 coordinates, or any othersuitable size. When mobile device 12 is a pager, the display may be evensmaller.

The mobile device 12 shown in FIG. 4 also includes a number of userinput keys or buttons (such as button 420) which allow the user toscroll through menu options or other display options which are displayedon display 402, or which allow the user to change applications or selectuser input functions, without contacting display 402.

Note that other forms of the mobile device are possible under thepresent invention. Examples include mobile phones that are capable ofperforming computing tasks, tablet PCs and wireless-enabled laptopcomputers, to name a few.

FIG. 5 is a more detailed block diagram of mobile device 12. Mobiledevice 12 illustratively includes microprocessor 506, memory 508,input/output (I/O) components 510, and communication links 26. Thesecomponents of mobile device 12 can be coupled for communication with oneanother over a suitable bus 516.

Memory 508 is illustratively implemented as nonvolatile electronicmemory such as random access memory (RAM) with a battery back-up module(not shown) such that information stored in memory 508 is not lost whenthe general power to mobile device 12 is shut down. A portion of memory508 is illustratively allocated as addressable memory for programexecution, while another portion of memory 508 is optionally used forstorage, such as to simulate storage on a disc drive.

Memory 508 can include operating system 518, one or more applicationprograms (such as PIM 16 and file application 18, etc.), as well asobject stores 20 and 22 and sync engine 24. During operation, operatingsystem 518 is illustratively executed by processor 506 from memory 48.The operating system 518 implements features which can be utilized byPIM 16 and file application 18 through a set of exposed applicationprogramming interfaces and methods. The objects in object stores 20 and22 are illustratively maintained by PIM 16, file application 18 andoperating system 518, at least partially in response to calls to theexposed application programming interfaces and methods.

I/O components 510, in one embodiment, are provided to facilitate inputand output operations from a user of mobile device 12. I/O components510 for various embodiments of mobile device 12 can include inputcomponents such as buttons and touch sensors and output components suchas a display, a speaker, and/or a printer port, etc.

Communication link 26 is any suitable communication interface. Interface26 is illustratively used to communicate with computing device 14 asdescribed with respect to FIG. 1. Memory 508 includes a set ofcommunication drivers 520 that interact with communication link 26 andthat translate data to and from the appropriate communication protocolnecessary to allow for communication across link 26.

FIG. 6 provides a block diagram showing communication link 26 andcommunication drivers 520 in more detail. In particular, FIG. 6 showscommunication link 26 as containing a number of communication ports 602,604, 606, 608 and 610 that communicate with devices outside of themobile device. Each port has an associated driver 612, 614, 616, 618,and 620, respectively, in communications drivers 520. IR port 602 and IRdriver 612 provide communication across an infrared communicationchannel between the mobile device and another computing device.Serial/USB port 604 and Serial/USB driver 612 provide communication overa serial or USB channel. Cable network port 606 and cable network driver616 provide communication over a network cable such as an Ethernetcable.

Wireless network port 608 and wireless network driver 618 providecommunication to a network over a radio channel. Wireless network port608 and driver 618 can use any number of wireless network protocolsincluding General Packet Radio Service (GPRS) and 1×rtt, which arewireless services used to provide cellular access to a network, as wellas 802.11 and 802.11b (Wi-Fi) protocols, and Bluetooth™ protocol, whichprovide local wireless connections to networks. Of course, others can beused as well.

SMS port 610 and SMS driver 620 support one-way communication using theShort Message Service protocol. Thus, SMS port 610 is able to receiveSMS messages that are broadcast using the radio spectrum.

Overview of Synchronization

FIG. 7 is a more detailed block diagram of sync engine 24 on mobiledevice 12 and sync engine 36 on desktop 14. Sync engine 24 on mobiledevice 12 includes synchronization manager 740, which is coupled to aset of application programs, such as PIM sync provider 744 and file syncprovider 746. PIM sync provider 744 is coupled to PIM object store 20,and file sync provider 746 is coupled to file object store 22.

Sync engine 36 on computing device 14 also includes a synchronizationmanager 748 coupled to an associated reference store 750 and alsocoupled to application programs, including PIM sync provider 752 andfile sync provider 754. PIM sync provider 752 is coupled to PIM objectstore 32, and file sync provider 754 is coupled to file object store 34.While providers 744, 746, 752 and 754 are shown coupled directly toassociated object stores, those providers could also be coupled to theobject stores through the application programs 16, 18, 28 and 30instead. However, for the sake of simplicity, the present discussionproceeds only with respect to the arrangement shown in FIG. 7.

Sync providers 752 and 754 expose application programming interfaces(APIs) 756 which can be called by sync manager 748 to read and storeobjects and object properties on object stores 32 and 34. The interfaces756 generally allow the creation of data bases for different types ofobjects, and allow application programs to read and write property namesand values to and from respective objects within each data base. Anumber of exemplary interfaces are now described, but form no part ofthe invention and are discussed for purposes of example and completenessonly.

The interfaces are well documented as the IReplStore, andIReplObjHandler interfaces. Each of these interfaces exposes a number ofwell documented methods. For example, the IReplStore interface exposes22 methods which can be generally classified as methods which are usedto access and modify the data store, methods used for objectenumeration, methods used to obtain object information, methods used tomanipulate handles to objects, methods used for user interfacefunctions, and a number of miscellaneous methods. The IReplObjHandlerinterface exposes methods which are used to serialize objects by turningan object into a series of bytes, and to deserialize objects by turningthe series of bytes back into an object. The methods included in theinterface are also used to delete an object from the correspondingobject store.

Sync manager 748, in turn, exposes a well documented interface known asthe IReplNotify interface to providers 752 and 754. This interfaceexposes four well documented methods which are used to notify syncmanager 748 of any change or deletion made to an object in acorresponding object store, to set text to be displayed in a status barwhere synchronization status can be observed by the user, to obtain awindow handle which is used as a parent window of any modal dialogue ormessage box, and to obtain information about a mobile device which hasbeen selected, or which is connected to the computing device.

Each of the providers 752 and 754 are implemented to specifically workin conjunction with a particular application program 28 or 34,respectively. In general, because the application program interface(API) 756 is standardized, it allows synchronization manager 748 toaccess and synchronize any number of different application programs, aslong as the required interface methods are implemented for eachapplication by corresponding providers.

On mobile device 12, providers 744 and 746 also provide the welldocumented IReplObjHandler interface such that objects in the associatedobject stores 20 and 22 can be serialized and deserialized. Providers744 and 746 also illustratively implement three additional functionswhich can be used to initialize and terminate the provider, to handleobject identification and change detection, and to retrieve deviceinformation about a particular object type. These functions andinterfaces are also well documented.

Synchronization manager 748 manipulates reference store 750 to maintaina mapping between instances of objects stored in object stores 32 and 34on computing device 14 and instances of the same objects stored inobject stores 20 and 22 on mobile device 12. Objects are identified byhandles which are created by providers 752 and 754. The handles areopaque to synchronization manager 748, in that synchronization manager748 need not be concerned with the actual composition of the handlesalthough the handles are manipulated and stored by synchronizationmanager 748.

Generally, in order to maintain the mapping, synchronization manager 748maintains reference store 750 so that it contains handles correspondingrespectively to a plurality of objects in the object stores 32 and 34 oncomputing device 14 which are to be synchronized with instances of thesame objects in object stores 20 and 22 on mobile device 12. The handlesin reference store 750 will typically correspond to objects that havebeen previously synchronized between the various object stores. Thehandles are updated after their corresponding objects have beensynchronized.

The list of handles maintained in reference store 750 is also used todetermine which items need to be synchronized to mobile device 12 thenext time mobile device 12 is connected to computing device 14. Inmaking this determination, synchronization manager 748 also determineswhether objects have been added to or deleted from the object stores sothat appropriate additions and deletions can be made.

The handles stored in reference store 750 may be formatted in accordancewith the following criteria so that the synchronization providers 752and 754 can perform the specified functions:

(a) Each handle may contain data that uniquely identifies an object—suchas an object identifier, an ID number, a full pathname for a file systemobject, etc. This data may be persistent (in that it does not change fora particular object) and should not be reused for subsequently createdobjects. This data can be compared to determine whether two handlesactually correspond to the same object. As is discussed below, this canbe problematic for file system information, because the objectidentifier is typically the pathname, and can be changed simply byrenaming the file.

(b) It may be possible to derive some object order based on the handle.

(c) The handle may have some sort of time stamp information, or versionnumber. This information can be compared to determine whether an objecthas changed since the last handle was recorded in reference store 750.

These handles are provided from providers 752 and 754 to synchronizationmanager 748, for storage in reference store 750, during an enumerationprocess which is described below. This enumeration process is used todetect items which need to by synchronized when mobile device 12 is nextcoupled to computing device 14.

FIGS. 8A and 8B are flow diagrams illustrating the enumeration processwhich is periodically performed by sync engine 36 in obtaining andupdating the list of handles stored in reference store 750 for thepurpose of determining which items need to synchronized upon nextconnection. After an initialization step indicated by block 860,synchronization manager 748 constructs two lists of handles. The firstlist is obtained at step 862 by accessing the handles previously storedin reference store 750 that correspond to objects that were previouslysynchronized. The second list of handles is obtained at step 864 byquerying each of the synchronization providers 752-754 using interfacemethods denoted by IReplObjHandler::FindFirstItem and FindNextItem. Whensuccessfully called, these interfaces enumerate an ordered list ofhandles corresponding respectively to a second group of objects, thoseobjects currently in the object stores 32 and 34 corresponding to theproviders 752 and 754 which have enumerated the objects.

By comparing the list of handles returned by the current enumerationwith the saved list of handles loaded from reference store 750,synchronization manager 748 automatically detects changes and deletions.For example, each time a new object is returned during enumeration,synchronization manager 748 attempts to find an object in its previouslysaved list of objects which represents the same object. If no matchinghandle is found, synchronization manager 748 determines that a newobject has been created and saved on the object store which enumeratedthe object under consideration. In order to determine whether matchinghandles are found, as is indicated by block 866, synchronization manager748 calls the interface method IReplStore::CompareItem.

Based on a comparison of the handles, synchronization manager 748creates any necessary handle-to-object mappings in reference store 750such that objects in the object stores on computing device 14 can bemapped to corresponding instances of the same object on device 12. Thisis indicated by block 868.

Synchronization manager 748 also determines whether any objects havebeen added, deleted, or modified in the particular object store fromwhich they were enumerated. This is indicated by blocks 870. Forexample, if the list of objects which were previously synchronizedcontains a handle that is not found in the newly created list based upona current enumeration of synchronization providers 752-754, thatindicates that the object has been deleted from the corresponding datastore 32, 34. Thus, synchronization manager 748 determines that theobject must also be deleted from the mobile device 12 during the nextsynchronization operation.

Similarly, if the enumeration of objects produces an object handle whichdocs not occur in the list of objects previously synchronized, thensynchronization manager 748 determines that an object corresponding tothat particular handle has been added to the object store whichenumerated the object. Thus, during the next synchronization operation,the object must be added to mobile device 12.

Synchronization manager 748 also calls the interface methodIReplStore::IsItemChanged with matching handles from the first andsecond lists. Calling this interface causes the appropriate provider 752or 754 (whichever enumerated the matching handle) to determine whetherthe object has changed since its handle was last written to referencestore 750. In one illustrative embodiment, the provider examines thetime stamp information or version number information associated with theobject handle. If that information is not identical, that indicates thatthere has been a change to the object. Thus, during the nextsynchronization process, synchronization manager 748 must update thecorresponding object on mobile device 12 (assuming there is no conflictas discussed below).

Synchronization manager 740 on mobile device 12 also interacts withsynchronization providers 744 and 746 to determine whether any objectson object stores 20 and 22 have been added, deleted, or changed sincethe last synchronization process. On mobile device 14, the operatingsystem posts a message to synchronization manager 740 every time anobject on mobile device 12, which is to be synchronized, changes, isadded, or is deleted. Synchronization manager 740 enumerates each objectand calls methods in the IreplNotify interface of each provider 744 and746. Based on this call, the provider determines whether the particularobject enumerated is to be synchronized and indicates to synchronizationmanager 740 how many objects are to be synchronized (for example, a filesystem object, such as a directory, actually contains more than oneobject which is to be synchronized).

Based on the notifications posted from the operating system,synchronization manager 740 maintains a list, or array, of objects whichhave changed, been deleted, or added since the last synchronizationprocess. Upon connection to computing device 14, this list is providedto synchronization manager 748. Thus, synchronization manager 748contains the lists which have been constructed for both desktop 14 andmobile device 12 which indicate objects which need to be synchronized.This is indicated by block 872 in FIG. 8B.

Synchronization manager 748 then determines, as indicated at block 874,whether an object has changed only on mobile device 12, only oncomputing device 14, or on both mobile device 12 and computing device14. If the object has changed only on one of the desktop object stores,then synchronization manager 748 carries out the necessary activity toupdate the corresponding object store on the mobile device. This isindicated by block 876. If the object has changed only on one of themobile device stores, then synchronization manager 748 carries out thenecessary activities to update the corresponding object store on thecomputing device 14. This is indicated by block 880.

However, if the same object has changed on both mobile device 12 andcomputing device 14, then a conflict situation arises. In oneillustrative embodiment, synchronization manager 748 makes a call to theregistry in the operating system of computing device 14 to obtainconflict information which instructs synchronization manager 748 how toproceed in the face of a conflict. This is indicated by block 878. Forexample, the user may have set preferences which indicate that, in thecase of a conflict either the desktop computer version, or the mobiledevice version should take precedence every time. Similarly, the usermay have set a preference which indicates that the user is to benotified in the case of a conflict so that the user can actively decidewhich version will take precedence. In that case, synchronizationmanager 748 generates a user interface allowing the user to resolve theconflict. Synchronization manager 748 then takes the necessary steps toresolve the conflict and update the appropriate object store. Thiscontinues until all objects in the lists of objects to be synchronizedhave been dealt with. This is indicated by block 882.

In order to exchange objects with mobile device 12, synchronizationmanager 748 continually calls the method IReplObjHandler:GetPacket tohave an appropriate provider 752 or 754 obtain a packet of informationto be transmitted to mobile device 12. To handle a packet received frommobile device 12, synchronization manager 748 callsIReplObjHandler::SetPacket. This acts to provide a packet of informationreceived from mobile device 12 to a synchronization provider 754 forstorage on its associated object store. Similar interfaces are called bysynchronization manager 740 on mobile device 12.

Scheduling Synchronization Operations

When performing synchronization operations over a wireless link, such asa cellular link, a number of concerns present themselves. First, it isdesirable that the user of the mobile device 12 has as up-to-dateinformation as possible. Therefore, frequent sync operations may bedesirable. However, sync operations require, in one embodiment, cellularconnection to a synchronization server. This can undesirably affect theremaining battery life of the mobile device 12, if it is necessary toconnect frequently. Similarly, cellular charges can undesirably increasethe cost of synchronization, especially when the mobile device isroaming relative to the synchronization server.

In one system, wireless synchronization operations were simply scheduledto be performed on a regular, periodic basis such as every two hours, orevery one hour, etc. However, this does not address all of the concerns.

One embodiment of the present invention provides a robust mobileschedule that, in various embodiments, includes a variety of differentfeatures to address the different concerns associated with schedulingsynchronization operations. For example, in one embodiment, a user canselect a frequency with which synchronization operations are to beperformed during different periods of the day (such as peak usage timeand off-peak usage time). Another feature of the present inventionallows the user to invoke a roaming override functionality in which aroaming synchronization schedule is implemented when the mobile deviceis roaming. Yet another embodiment of the present invention allows theuser to configure the mobile device to force a synchronization operationeach time one of a predefined subset of operations is performed thattriggers a synchronization operation.

FIG. 9 shows one embodiment of a user interface 900 generated on amobile device 12 for setting the frequencies with which synchronizationoperations are performed during different times of the day, and when themobile device 12 is roaming. User interface 900 includes a peak timesync field 902, and off peak sync field 904 and a roaming sync field906. User interface 900 also includes peak times setting button 908.

In one embodiment, the user can select which times of day are peak timesand which times are non-peak times. For instance, it is believed thatwhen a user is working and receiving large numbers of electronic mailmessages, it is likely that the user may want to have synchronizationoperations performed frequently to ensure that the information they areviewing and manipulating is up-to-date. However, during non-work hours,the user may not be as concerned as to whether the data is up-to-date.However, some users desire data that is up-to-date regardless of whetherit is a peak or non-peak time.

The user sets peak and non-peak times using button 908. If the useractuates button 908, another user interface appears which allows theuser to designate which hours of the day are peak times. The remaininghours can be assumed to be non-peak times, or non-peak times can bedesignated by the user as well. Once the peak and non-peak times havebeen identified by the user, the user can actuate the buttons withinfields 902 and 904 to adjust the frequency (during peak and non-peaktimes) with which synchronization operations are to be performed.

The user may wish to have these schedules overridden when certaincriteria are present. For instance, by actuating the button in field906, the user can select a sync schedule that is to be implemented whenthe mobile device is roaming. For example, the user can select aschedule which only synchronizes when the user manually triggers asynchronization process. Alternatively, the synchronization operationscan be set completely to be completely precluded while the mobile deviceis roaming, or they can be set to a specific frequency, chosen by theuser.

FIG. 10 is a flow diagram better illustrating how the sync schedulingworks on the mobile device 12. First, a synchronization operation istriggered, such as by reaching a time when the next sync is scheduled.This is indicated by block 910. Next, it is determined whether the syncis even possible based on system status. For example, if the cellularradio circuitry on the mobile device 12 has been turned off, or if theuser is on a voice telephone call, of if the synchronization network issomehow unavailable, then synchronization is not possible. In that case,a next synchronization is scheduled based on re-try logic which isdescribed in greater detail below. Determining whether the sync ispossible and syncing based on re-try logic is indicated by blocks 912and 914 in FIG. 10.

If, at block 912, it is determined that the synchronization process ispossible, then it is determined whether any override criteria arepresent, in this case, whether the mobile device 12 is roaming. This isindicated by block 916. If the device is roaming, then it is determinedwhether the user has selected one of the roaming override functions infield 906 of the user interface 900 shown in FIG. 9. This is determinedby block 918. If so, then synchronization is performed according to theroaming override schedule, as indicated by block 920. For example, ifsynchronization is only to be performed when it is manually initiated,then the synchronization operation is not performed until that occurs.

If, at block 916 it is determined that the mobile device is not roaming,or, at block 918 it is determined that the user has not selected aroaming override function, then the synchronization operation isperformed as indicated by block 922. If the synchronization isinterrupted or fails, this is determined at block 924 and anothersynchronization operation is scheduled based on the re-try logic.

The re-try logic can be any suitable logic algorithm. For instance, onesuch algorithm will initiate a re-try after a minimum desired time lapse(such as three minutes) and a maximum desired re-try time (which isequal to the next scheduled sync time). For example, assume that themobile device 12 is operating in non-peak time and that it is scheduledto sync every 60 minutes during non-peak time. Assume that a syncoperation is triggered and that the sync operation fails. One exemplaryalgorithm retries the sync operation at intervals of three minutes, sixminutes, twelve minutes, twenty-four minutes, forty-eight minutes andsixty minutes. The last re-try interval is not ninety-six minutes,because the user has scheduled the sync operations to occur every sixtyminutes.

If, at block 924, the sync has not failed, but is successful, then thenext sync timer is scheduled in accordance with whether it is currentlypeak or non-peak time and the user's selections as illustrated withrespect to FIG. 9. This is indicated by block 926.

In accordance with one embodiment of the present invention, sync timersare triggered based on the starting time of a current sync operation.For example, if the present sync operation starts at 10:00 a.m., andsync operations are scheduled to be performed every five minutes, thenthe next sync operation is triggered at 10:05 a.m., regardless of howlong the current sync operation took to perform. This can bedisadvantageous, however. For example, if the current sync operationtakes 4.5 minutes, then the next sync operation will be triggered 30seconds after the current sync operation concludes. This can have theundesirable results of tying up the mobile device 12 more frequentlythan necessary, draining the battery faster than necessary, andconsuming synchronization server time.

Therefore, in accordance with another embodiment of the presentinvention, the next sync timer is scheduled at block 926 beginning fromthe end of the current sync operation. Therefore, if the current syncoperation started at 10:00 a.m. and finished at 10:03 a.m., and the synctimers are scheduled to be set every five minutes, then the next synctimer will be scheduled to trigger at 10:08 a.m.

When synchronizing on a mobile schedule, where synchronizationoperations occur at regular time intervals, it is possible that asignificant amount of time can elapse between synchronizationoperations. However, between synchronization operations, a user may wellbe composing, forwarding and replying to electronic mail messages, aswell as possibly marking some messages or attachments for download, andsending and responding to meeting requests. To compensate for the timedifference between a current action of the user and the next scheduledmeeting request, the mobile device can be configured to schedule meetingrequests based on actions taken by the user, instead of simply based onelapsed time.

In accordance with another embodiment of the present invention, the usercan configure the mobile device to initiate a sync operation when one ofa preselected subset of operations is performed on the mobile devicethat would otherwise trigger a sync. In other words, there are a widevariety of different operations which can be taken on the mobile deviceand which would normally trigger a sync operation. The user may simplyread a message, delete a message, reply to a message, forward a message,etc. While all of these operations would normally trigger a syncoperation, it may not be desirable to initiate an immediate syncoperation for all of these. For example, it may not be desirable toinitiate an immediate, remote sync operation simply when the userdeletes a message from the In-Box of an electronic mail applicationprogram. Similarly, it may not be desirable to initiate an immediate,remote sync simply because the user selects an electronic mail operationto read. However, it may be desirable to initiate such a synchronizationoperation during other actions, such as those that send an electronicmail transmission, or such as when an attachment or electronic mailmessage is selected to be downloaded to the mobile device 12. Suchactions can include, for example, sending a new electronic mail message,replying to or forwarding an electronic mail message, responding tomeeting requests or generating a meeting request, requesting more datafrom an item, such as a body of message text or attachments, to be downloaded, etc.

FIGS. 11-12C illustrate an embodiment of the present invention in whichthese actions can be used to initiate a synchronization operation.First, the user takes an action which triggers a synchronizationoperation. This is indicated by block 1000. As mentioned, these actionswill likely be a preselected subset of actions which the user can takeon the mobile device, and maybe those actions which generate an outgoingelectronic mail message, or identify information to be downloaded.

It is next determined whether the real time response feature thatautomatically initiates a synchronization operation based on theseactions (rather than waiting for the next scheduled sync operation) isactive. This is indicated by block 1002. FIGS. 12A-12C illustratedifferent user interfaces which allow the user to select the real timeresponse feature. FIG. 12A is similar to FIG. 9, except that it alsoincludes a box labeled “Sync outgoing items as they are sent”. This isdesignated by number 1100 in FIG. 12A. If the user checks this box, thensynchronization operations are initiated when the user takes any of thepredetermined subset of actions that trigger a real time responsesynchronization operation. FIG. 12B is simply a different embodiment ofa user interface but also contains the check box 1100, as does the userinterface indicated in FIG. 12C.

It should be noted that it may be desirable to schedule real timeresponse synchronization operations based on the user's actions, notimmediately, but after a predetermined, relatively short, time delay.This time delay can be specified by the user, or it can be automaticallyset by the mobile device 12. For example, the user may be responding toa large number of emails at one time. Therefore, the synchronizationoperation may illustratively be delayed for a short period of time, suchas five minutes, after the user has responded to an electronic mailmessage. This facilitates batching items which are to be synchronizedfrom the mobile device. This reduces the frequency with which thewireless connection to the synchronization server must be establishedand torn down.

In any case, once the user takes an action which triggers thesynchronization operation at block 1000, it is determined whether theuser has selected the real time response feature on the user interfacesshown in FIGS. 12A-12C. This is indicated by block 1002. If the user hasnot selected these features, then a full synchronization operation issimply performed on the next scheduled synchronization timer. This isindicated by block 1004.

If, however, at block 1002, it is determined that the user has selectedthe real time response feature, then it is determined whether the nextregularly scheduled synchronization operation is scheduled to triggersooner than the real time response timer. In other words, if the delaytime between an action triggering a synchronization operation under thereal time response feature is longer than the delay to the nextregularly schedule synchronization operation, this is determined atblock 1006. If so, that means that the next regularly scheduledsynchronization operation will actually take place before the real timeresponse timer would trigger a synchronization operation. Therefore, thenormal, regularly scheduled synchronization operation is simplyperformed as scheduled at block 1004.

If, however, the real time response timer would schedule thesynchronization operation prior to the next regularly scheduledoperation, then the real time response synchronization timer is set, asindicated by block 1008, and synchronization is performed at that time.In one illustrative embodiment, the next regularly scheduledsynchronization is not altered, even if the real time responsesynchronization timer schedules an earlier synchronization operation.However, this could be modified as well so that the next regularlyscheduled synchronization operation is delayed for a predetermined delaytime after the real time response synchronization timer has triggered asynchronization operation.

It should be noted that, in one illustrative embodiment, thesynchronization operations discussed herein can be backgroundsynchronization operations. In that embodiment, no user interface itemsinterrupt the user, and the synchronization operations are performedpurely in the background.

Although the present invention has been described with reference topreferred embodiments, workers skilled in the art will recognize thatchanges may be made in form and detail without departing from the spiritand scope of the invention

1.-20. (canceled)
 21. A device, comprising: at least one processor; anda memory coupled to the at least one processor and storing instructionsthat, when executed by the at least one processor, perform a method,comprising: detecting execution of an operation; determining whether theoperation is one of a subset of operations that causes a synchronizationoperation to be performed when the operation is executed; and when it isdetermined that the operation is one of the subset of operations thatcauses a synchronization operation to be performed, performing thesynchronization operation.
 22. The device of claim 21, furthercomprising instructions for detecting an input that indicates whetherthe execution of the operation causes the synchronization to beperformed.
 23. The device of claim 21, further comprising instructionsfor scheduling the synchronization operation when it is determined thatthe operation is not one of the subset of operations.
 24. The device ofclaim 21, wherein the operation is performed by an electronic messageapplication.
 25. The device of claim 21, wherein the operation is one ormore of: a selection of an electronic message; sending an electronicmessage; or deleting an electronic message
 26. The device of claim 21,further comprising instructions for associating a time delay with thesynchronization operation.
 27. The device of claim 26, furthercomprising instructions for comparing the time delay of thesynchronization operation to a time frame associated with the scheduledsynchronization operation specified by the synchronization schedule. 28.The device of claim 27, further comprising instructions for executingthe scheduled synchronization operation in lieu of the synchronizationoperation when an amount of time remaining in the time frame is lessthan the time delay.
 29. A method, comprising: receiving, in a userinterface, input that provides a synchronization setting for an actionassociated with a preselected subset of actions; detecting execution ofthe action; and when the synchronization setting indicates asynchronization operation is to be performed when the action isexecuted, performing the synchronization operation.
 30. The method ofclaim 29, further comprising determining whether a synchronizationschedule is associated with the action.
 31. The method of claim 30,further comprising performing the synchronization operation prior to ascheduled synchronization operation specified by the synchronizationschedule.
 32. The method of claim 29, wherein the action is associatedwith an electronic message application executing on the computingdevice.
 33. The method of claim 32, wherein the action is one or more ofsending an electronic message, replying to a received electronicmessage; downloading an attachment in an electronic message; generatinga meeting request or responding to a meeting request.
 34. The method ofclaim 29, further comprising receiving input that changes thesynchronization setting.
 35. A computing device, comprising: at leastone processor; and a memory coupled to the at least one processor andstoring instructions that, when executed by the at least one processor,perform a method, comprising: detecting an operation performed by thecomputing device; determining whether the operation is one of apreselected subset of operations for which a synchronization setting hasbeen indicated; and performing a synchronization operation in responseto the operation being performed by the computing device, theperformance of the synchronization operation being based, at least inpart, on the synchronization setting.
 36. The computing device of claim35, further comprising receiving input that changes the synchronizationsetting.
 37. The computing device of claim 35, wherein thesynchronization setting indicates the synchronization operation ispreformed substantially immediately after the operation is performed bythe computing device.
 38. The computing device of claim 35, wherein thesynchronization setting indicates the synchronization operation is to beperformed according to a schedule.
 39. The computing device of claim 35,wherein the operation is associated with an electronic messagingapplication.
 40. The computing device of claim 35, further comprisinginstructions for providing a user interface on the computing device, theuser interface displaying input mechanisms that, when selected, indicatethe synchronization setting.